|
•
|
Counter: A counter records incremental data cumulatively and rolls over when the counter limit is reached.
|
|
•
|
Gauge: A gauge statistic indicates a single value; a snapshot representation of a single point in time within a defined time frame. The gauge changes to a new value with each snapshot though a value may repeat from one period to the next. The limit depends upon the data type.
|
|
•
|
Information: This type of statistic provides information, often intended to differentiate sets of statistics; for example, a VPN name or IP address. The type of information provided depends upon the data type.
|
|
•
|
Int32/Int64: An integer, either 32-bit or 64-bit:
|
|
•
|
|
•
|
Float: A numeric value that can be represented fractionally; for example, 1.345.
|
|
•
|
String: A series of ASCII alphanumeric characters in a single grouping, usually pre-configured.
|
Important: Unless otherwise indicated, all statistics are counters and all statistics are standards-based.|
Description: The name of the context configured on the system that is currently facilitating the LMA service.
Type: Information
|
||
|
Description: The identification number of the context configured on the system that is currently facilitating the LMA service. This is an internal reference number.
Type: Information
|
||
|
Description: Displays the name of the LMA service for which the statistics are displayed.
Type: Information
|
||
|
Description: The identification number of the service configured on the system that is currently facilitating the LMA service. This is an internal reference number.
Type: Information
|
||
|
Description: The total number of sessions currently active in the LMA service.
Availability: per LMA service
Type: Gauge
|
||
|
Description: The total number of mobile IP AAA Authentication attempts on receiving Binding request message by LMA service.
Triggers: Increments when auth attempted on receiving Bind message.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of successful mobile IP AAA Authentication attempts made by LMA service.
Triggers: Increments when auth is successful when attempted.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of failed mobile IP AAA authentication attempts received by LMA service.
Triggers: Increments when auth failed when attempted.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of mobile IP AAA authentication failures received by LMA service.
Triggers: Increments when actual auth failed when attempted.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of miscellaneous mobile IP AAA authentication failures received by LMA service.
Triggers: Increments when auth failed due to other reasons when attempted.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of all binding updates received by LMA service.
Triggers: Increments when binding updated request is received.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of all binding updates received and accepted by LMA service.
Triggers: Increments when binding update request is accepted.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of all binding updates received and denied by LMA service.
Triggers: Increments when binding update request is rejected/denied.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of all binding updates received and discarded by LMA service.
Triggers: Increments when binding update request is discarded.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of all initial binding updates received by LMA service.
Triggers: Increments when initial binding updated request is received.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of initial binding updates received and accepted by LMA service.
Triggers: Increments when initial binding update request is accepted.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of initial binding updates received and denied by LMA service.
Triggers: Increments when initial binding update request is rejected/denied.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of all refresh binding update requests received by LMA service.
Triggers: Increments when renew binding updated request is received.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of refresh binding update requests received and accepted by LMA service.
Triggers: Increments when renew binding update request is accepted.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of refresh binding update requests received and denied by LMA service.
Triggers: Increments when renew binding update request is rejected/denied.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of all deregistration request binding updates received by LMA service.
Triggers: Increments when dereg binding updated request is received.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of deregistration request binding updates received and accepted by LMA service.
Triggers: Increments when dereg binding update request is accepted.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of deregistration request binding updates received and denied by LMA service.
Triggers: Increments when dereg binding update request is rejected/denied.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of all handoff request binding updates received by LMA service.
Triggers: Increments when handoff binding updated request is received.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of handoff request binding updates received and accepted by LMA service.
Triggers: Increments when handoff binding update request is accepted.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of handoff request binding updates received and denied by LMA service.
Triggers: Increments when handoff binding update request is rejected/denied.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of all binding update acknowledgements sent by LMA service.
Triggers: Increments when binding Ack is sent.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of accepted registration binding update acknowledgements sent by LMA service.
Triggers: Increments when binding Ack is sent with success status code.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of accepted deregistration binding update acknowledgements sent by LMA service.
Triggers: Increments when dereg binding Ack is sent with success status code.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of denied binding update acknowledgements sent by LMA service.
Triggers: Increments when binding Ack is denied and sent with error status code.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of send error binding update acknowledgements sent by LMA service.
Triggers: Increments when error is encountered while sending binding Ack.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of binding update deny messages, due to insufficient resources, sent by LMA service.
Triggers: Increments when Binding Ack is sent with status code “Insufficient resources”.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of binding update deny messages, due to mismatched IDs, sent by LMA service.
Triggers: Increments when Binding Ack is sent with status code “Mismatched ID”.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of binding update deny messages, due to a mobile node authentication failure condition, sent by LMA service.
Triggers: Increments when Binding Ack is sent with status code “Mobility Auth failed”.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of binding update deny messages, due to an admin prohibited condition, sent by LMA service.
Triggers: Increments when Binding Ack is sent with status code “Admin Prohibited”.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of binding update deny messages, due to requiring a message ID, sent by LMA service.
Triggers: Increments when Binding Ack is sent with status code “Mesg ID Reqd”.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of binding update deny messages, due to DAD failure, sent by LMA service.
Triggers: Increments when Binding Ack is sent with status code “DAD failed”.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of binding update deny messages, due to an incorrect home subnet, sent by LMA service.
Triggers: Increments when Binding Ack is sent with status code “Not Home Subnet”.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of binding update deny messages, due to sequence out of window, sent by LMA service.
Triggers: Increments when Binding Ack is sent with status code “Sequence Number out of window”.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of binding update deny messages, due to a disallowed registration type change, sent by LMA service.
Triggers: Increments when Binding Ack is sent with status code “Reg Type change Disallowed”.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of binding update deny messages, due to an unspecified reason, sent by LMA service.
Triggers: Increments when Binding Ack is sent with status code “Unspecified reason”.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of binding update deny messages, due to a service authorization failure, sent by LMA service.
Triggers: Increments when Binding Ack is sent with status code “Service authorization failed”.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of binding update deny messages, due to a proxy registration not enabled error, sent by LMA service.
Triggers: Increments when Binding Ack is sent with status code “Proxy Reg Not enabled”.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of binding update deny messages, due to a timestamp mismatch error, sent by LMA service.
Triggers: Increments when Binding Ack is sent with status code “Timestamp mismatch”.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of binding update deny messages, due to a timestamp lower than expected reason, sent by LMA service.
Triggers: Increments when Binding Ack is sent with status code “Timestamp lower than expected”.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of binding update deny messages, due to a missing MN-ID option, sent by LMA service.
Triggers: Increments when Binding Ack is sent with status code “Missing MN-ID option”.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of binding update deny messages, due to a missing HNP option, sent by LMA service.
Triggers: Increments when Binding Ack is sent with status code “Missing HNP option”.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of binding update deny messages, due to a missing access technology option, sent by LMA service.
Triggers: Increments when Binding Ack is sent with status code “Missing Access Tech option”.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of binding update deny messages, due to a missing handoff indicator option, sent by LMA service.
Triggers: Increments when Binding Ack is sent with status code “Missing Handoff indication option”.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of binding update deny messages, due to a not authorized for HNP reason, sent by LMA service.
Triggers: Increments when Binding Ack is sent with status code “Not Authorized for HNP”.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of binding update deny messages, due to a missing LMA for the MN, sent by LMA service.
Triggers: Increments when Binding Ack is sent with status code “Not LMA for mobile”/
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of binding update deny messages, due to a not authorized for proxy registration reason, sent by LMA service.
Triggers: Increments when Binding Ack is sent with status code “Not Authorized for Proxy Reg”.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of binding update deny messages, due to a BCE prefix not matching, sent by LMA service.
Triggers: Increments when Binding Ack is sent with status code “BCE prefix set do not match”.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of binding update deny messages, due to a GRE key option required, sent by LMA service.
Triggers: Increments when Binding Ack is sent with status code “GRE key option required”.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of binding update deny messages, due to insufficient resources - no session manager, sent by LMA service.Increments when Binding Update rejected due to No sessmgr.
Triggers: Increments when Binding Update rejected due to No sessmgr.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of binding update deny messages, due to insufficient resources - no memory, sent by LMA service.
Triggers: Increments when Binding Update rejected due to memory alloc failure.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of binding update deny messages, due to insufficient resources - session manager rejected, sent by LMA service.
Triggers: Increments when Binding Update rejected due to sessmgr rejection.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of binding update deny messages, due to insufficient resources - input queue exceeded, sent by LMA service.
Triggers: Increments when Binding Update rejected due to demux queue exceeding limit.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of binding update deny messages, due to insufficient resources - simultaneous bindings exceeded, sent by LMA service.
Triggers: Increments when Binding Update rejected due to session exceeding binding limit.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of binding update deny messages, due to insufficient resources - address allocation failed, sent by LMA service.
Triggers: Increments when Binding Update rejected due to address alloc failure.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of binding update deny messages, due to an administrator prohibited - MN-AAA auth option missing condition, sent by LMA service.
Triggers: Increments when Binding Update rejected due to missing MN-AAA auth option.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of binding update deny messages, due to an administrator prohibited - H-bit not set condition, sent by LMA service.
Triggers: Increments when Binding Update rejected due to H bit not set.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of binding update deny messages, due to an administrator prohibited - invalid MN-AAA option SPI condition, sent by LMA service.
Triggers: Increments when Binding Update rejected due to invalid SPI in MN-AAA auth option.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of binding update deny messages, due to an administrator prohibited - invalid MN-HA option SPI condition, sent by LMA service.
Triggers: Increments when Binding Update rejected due to invalid SPI in MN-HA auth option.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of binding update deny messages, due to an administrator prohibited - congestion control condition, sent by LMA service.
Triggers: Increments when Binding Update rejected due congestion control.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of binding update deny messages, due to an administrator prohibited - policy rejected condition, sent by LMA service.
Triggers: Increments when Binding Update rejected due policy.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of binding update deny messages, due to an administrator prohibited - HoA not authorized condition, sent by LMA service.
Triggers: Increments when Binding Update rejected due HoA authorization failure.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of binding update deny messages, due to an administrator prohibited - no permission condition, sent by LMA service.
Triggers: Increments when Binding Update rejected due to no permission.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of binding update deny messages, due to an administrator prohibited - bad request condition, sent by LMA service.
Triggers: Increments when Binding Update decode fails.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of binding update discarded messages, due to congestion, sent by LMA service.
Triggers: Increments when Binding Update discarded due to congestion control.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of binding update discarded messages, due to checksum error(s), sent by LMA service.
Triggers: Increments when Binding Update discarded due to checksum error
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of binding update discarded messages, due to an initial authentication pending condition, sent by LMA service.
Triggers: Increments when Binding Update discarded when initial registration is still being processed.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of binding update discarded messages, due to a session not found condition, sent by LMA service.
Triggers: Increments when Binding Update discarded due to session not found internally when expected.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of binding update discarded messages, due to an HA manager not found condition, sent by LMA service.
Triggers: Increments when Binding Update discarded due to hamgr not ready.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of binding update discarded messages, due to a decode failure, sent by LMA service.
Triggers: Increments when Binding Update discarded due to decode failure.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of binding update discarded messages, due to an invalid buffer length, sent by LMA service.
Triggers: Increments when Binding Update discarded due to packet buffer length.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of binding update discarded messages, due to a revocation pending, sent by LMA service.
Triggers: Increments when Binding Update discarded due to pending revocation.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of binding revocations sent by LMA service.
Triggers: Increments when initial Binding Revocation indication is sent.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of binding revocation retries sent by LMA service.
Triggers: Increments when Binding Revocation indication message is retried.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of binding revocation acknowledgements received by LMA service.
Triggers: Increments when Binding Revocation Acknowledgement is received.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of binding revocations sent, but not acknowledged, by LMA service.
Triggers: Increments when session deleted without receiving ACK after max retries.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of binding revocations received by LMA service.
Triggers: Increments when Binding revocation indication is received.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of binding revocation acknowledgements sent by LMA service.
Triggers: Increments when Binding revocation Acknowledgement is sent.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of Binding Revocation Indication (BRI) messages sent by LMA service with a “Reserved” revocation trigger reason.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of Binding Revocation Indication (BRI) messages sent by LMA service with an “Unspecified” revocation trigger reason.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of Binding Revocation Indication (BRI) messages sent by LMA service with an “Administrative Reason” revocation trigger reason.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of Binding Revocation Indication (BRI) messages sent by LMA service with an “Inter-MAG Handoff-Same ATT” revocation trigger reason.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of Binding Revocation Indication (BRI) messages sent by LMA service with an “Inter-MAG - Unknown Handoff” revocation trigger reason.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of Binding Revocation Indication (BRI) messages sent by LMA service with an “Inter-MAG Handoff-Diff ATT” revocation trigger reason.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of Binding Revocation Indication (BRI) messages sent by LMA service with a “Per-Peer Policy” revocation trigger reason.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of Binding Revocation Indication (BRI) messages sent by LMA service with a “Revoking Node Local Policy” revocation trigger reason.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of Binding Revocation Indication (BRI) messages sent by LMA service with a “User Initiated Session Term” revocation trigger reason.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of Binding Revocation Indication (BRI) messages sent by LMA service with an “Access Network Session Term” revocation trigger reason.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of Binding Revocation Indication (BRI) messages sent by LMA service with an “IPv4 HoA Binding Only” revocation trigger reason.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of Binding Revocation Indication (BRI) messages sent by LMA service with an “Out-of Sync BCE State” revocation trigger reason.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of Binding Revocation Indication (BRI) messages sent by LMA service with an “Unknown” revocation trigger reason.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of Binding Revocation Acknowledgement (BRA) messages received by LMA service with a “Success” status.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of Binding Revocation Acknowledgement (BRA) messages received by LMA service with a “Partial-Success” status.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of Binding Revocation Acknowledgement (BRA) messages received by LMA service with a “Binding-Does-Not-Exist” status.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of Binding Revocation Acknowledgement (BRA) messages received by LMA service with a “No IPv4-HoA-Bind” status.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of Binding Revocation Acknowledgement (BRA) messages received by LMA service with a “Global-Revoc-Not-Authorized” status.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of Binding Revocation Acknowledgement (BRA) messages received by LMA service with a “Cannot-Identify-Binding” status.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of Binding Revocation Acknowledgement (BRA) messages received by LMA service with a “Revoc-Failed-MN-Attached” status.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of Binding Revocation Acknowledgement (BRA) messages received by LMA service with an “Unknown” status.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of binding revocation acknowledgements received and discarded by LMA service.
Triggers: Increments when Binding revocation Acknowledgement is discarded.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of binding revocation acknowledgements received and discarded, due to a session not found condition, by LMA service.
Triggers: Increments when Binding revocation Acknowledgement discarded due to session not found.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of binding revocation acknowledgements received and discarded, due to a badly formed request condition, by LMA service.
Triggers: Increments when Binding revocation Acknowledgement discarded due to badly formed message.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of binding revocation acknowledgements received and discarded, due to a decode error condition, by LMA service.
Triggers: Increments when Binding revocation Acknowledgement discarded due to decode failure.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of binding revocation acknowledgements received and discarded, due to a checksum error condition, by LMA service.
Triggers: Increments when Binding revocation Acknowledgement discarded due to checksum error.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of binding revocation acknowledgements received and discarded, due to a invalid memory type condition, by LMA service.
Triggers: Increments when Binding revocation Acknowledgement discarded due to invalid message type.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of binding revocation acknowledgements received and discarded, due to a HAMGR not ready condition, by LMA service.
Triggers: Increments when Binding revocation Acknowledgement discarded due to HAMGR not ready.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of binding revocation acknowledgements received and discarded, due to a matching request not found condition, by LMA service.
Triggers: Increments when Binding revocation Acknowledgement discarded as matching request not found.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of binding revocation acknowledgements received and discarded, due to a invalid buffer length condition, by LMA service.
Triggers: Increments when Binding revocation Acknowledgement discarded due to invalid packet length.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of packets received by LMA service.
Triggers: Increments when tunneled data packet is received.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of IPv6-in-IPv6 tunnel packets received by LMA service.
Triggers: Increments when tunneled IPv6 in IPv6 encapsulated data packet is received.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of IPv4-in-IPv6 tunnel packets received by LMA service.
Triggers: Increments when tunneled IPv4 in IPv6 encapsulated data packet is received.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of IPv4-in-IPv6 GRE tunnel packets received by LMA service.
Triggers: Increments when tunneled IPv4 in IPv6 GRE encapsulated data packet is received.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of IPv6-in-IPv6 GRE tunnel packets received by LMA service.
Triggers: Increments when tunneled IPv6 in IPv6 GREncapsulated data packet is received.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of octets received by LMA service.
Triggers: Increments with number of bytes received when tunneled data packet is received.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of IPv6-in-IPv6 tunnel octets received by LMA service.
Triggers: Increments with number of IPv6 in IPv6 bytes received when tunneled data packet is received.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of IPv4-in-IPv6 tunnel octets received by LMA service.
Triggers: Increments with number of IPv4 in IPv6 bytes received when tunneled data packet is received.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of IPv4-in-IPv6 GRE tunnel octets received by LMA service.
Triggers: Increments with number of IPv4 in IPv6 GRE bytes received when tunneled data packet is received.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of IPv6-in-IPv6 GRE tunnel octets received by LMA service.
Triggers: Increments with number of IPv6 in IPv6 GRE bytes received when tunneled data packet is received.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of data errors received by LMA service.
Triggers: Increments when error is encountered on processing data packet received from the tunnel.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of protocol type data errors received by LMA service.
Triggers: Increments when packet received with invalid protocol type.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of invalid packet length data errors received by LMA service.
Triggers: Increments when packet received with invalid length.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of no session found data errors received by LMA service.
Triggers: Increments when packet received with session not found.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of packets sent by LMA service.
Triggers: Increments when tunneled data packet is sent.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of IPv6-in-IPv6 tunnel packets sent by LMA service.
Triggers: Increments when tunneled IPv6 in IPv6 encapsulated data packet is sent.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of IPv4-in-IPv6 tunnel packets sent by LMA service.
Triggers: Increments when tunneled IPv4 in IPv6 encapsulated data packet is sent.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of IPv4-in-IPv6 GRE tunnel packets sent by LMA service.
Triggers: Increments when tunneled IPv4 in IPv6 GRE encapsulated data packet is sent.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of IPv6-in-IPv6 GRE tunnel packets sent by LMA service.
Triggers: Increments when tunneled IPv6 in IPv6 GREncapsulated data packet is sent.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of octets sent by LMA service.
Triggers: Increments with number of bytes sent when tunneled data packet is sent.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of IPv6-in-IPv6 tunnel octets sent by LMA service.
Triggers: Increments with number of IPv6 in IPv6 bytes sent when tunneled data packet is sent.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of IPv4-in-IPv6 tunnel octets sent by LMA service.
Triggers: Increments with number of IPv4 in IPv6 bytes sent when tunneled data packet is sent.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of IPv4-in-IPv6 GRE tunnel octets sent by LMA service.
Triggers: Increments with number of IPv4 in IPv6 GRE bytes sent when tunneled data packet is sent.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of IPv6-in-IPv6 GRE tunnel octets sent by LMA service.
Triggers: Increments with number of IPv6 in IPv6 GRE bytes sent when tunneled data packet is sent.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of tunnel ICMP packets - too big received by LMA service.
Triggers: Increments when packet too big received with tunnel.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of tunnel ICMP packets - too big dropped by LMA service.
Triggers: Increments when packet too big received with tunnel is dropped.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of tunnel ICMP packets - too big relayed by LMA service.
Triggers: Increments when packet too big received with tunnel is relayed.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of disconnects initiated by LMA service.
Triggers: Increments when LMA session disconnects.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of disconnects due to lifetime expiry initiated by LMA service.
Triggers: Increments when LMA session is disconnected due to lifetime expiry.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number sessions disconnected in the LMA service due to peer deregistration.
Triggers: Increments when LMA session is disconnected due to deregistration.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of disconnects due to admin drops initiated by LMA service.
Triggers: Increments when LMA session disconnects due to Admin reasons.
Availability: per LMA service
Type: Counter
|
||
|
Description: The total number of disconnects due to “other reasons” initiated by LMA service.
Triggers: Increments when LMA session is disconnected due to misc reasons.
Availability: per LMA service
Type: Counter
|
||
 Important: See Bulk Statistics Overview for statistics that are common to all schema. |
||
